Import image via COS#68
Conversation
mjturek
force-pushed
the
import-from-cos
branch
from
46b5186 to
e1d183c
Compare
|
can you remove the vendoring? |
I can but then it will not pass CI |
|
if you just run |
mjturek
force-pushed
the
import-from-cos
branch
2 times, most recently
from
1305628 to
5455301
Compare
mjturek
force-pushed
the
import-from-cos
branch
4 times, most recently
from
158b2e7 to
337be97
Compare
|
what instlal-config.yaml changes do we need to use this? |
You just need to set the Currently if you want to use a specific region for the bucket, you can specify it in |
mjturek
force-pushed
the
import-from-cos
branch
2 times, most recently
from
1d0a3f8 to
014966a
Compare
mjturek
force-pushed
the
import-from-cos
branch
from
014966a to
0defb4f
Compare
There was a problem hiding this comment.
masterConfig.Image should be the boot image we create, and not the ova. so this should stay as ImageName, and we'll need a new field for the bucket object name (ImageBucketFileName is fine). ImageName will be the same as pi_image_name ("${var.cluster_id}-boot-image"). ImageBucketFileName will need to come down from the bits that Cory is working on I believe.
There was a problem hiding this comment.
until we have the rhcos bits from cory, what about setting the default to the current ova, and it'll then be easily change if we need to update it before that PR lands?
There was a problem hiding this comment.
That sounds good to me, changing now
mjturek
force-pushed
the
import-from-cos
branch
from
0defb4f to
6481470
Compare
mjturek
force-pushed
the
import-from-cos
branch
from
6481470 to
34e83f5
Compare
2 participants
No description provided.